Hardware-Initiated Automated Back-Up of Data from an Internal Memory of a Hand-Portable Electronic Device

ABSTRACT

A hand-portable electronic device configured for hardware-initiated automated back-up, comprising: an internal memory for storing data; an interface for connection and disconnection to any one of a plurality of generic memory modules; a user interface that enables a user of the device to specify the generic memory module connected to the interface for automated back-up of data stored in the internal memory; a controller for automatically backing up data, on connection of a generic memory module to the interface, from the internal memory to the connected generic memory module if the connected generic memory module is identified as a generic memory module that has previously been specified for back-up via the user interface.

FIELD OF THE INVENTION

Embodiments of the present invention relate to hardware-initiatedautomated back-up of data from an internal memory of hand-portableelectronic device. In particular, embodiments of the invention relate tomethods for backing-up data from internal memories of hand-portableelectronic devices and also to hand-portable electronic devicesconfigured for hardware-initiated automated back-up.

BACKGROUND TO THE INVENTION

U.S. Pat. No. 6,249,863 and U.S. Pat. No. 5,795,156 disclose thehardware-initiated automated launch of an application. A host device hasan installed autostart driver. When a storage media is inserted into adrive of the host device, the autostart driver automatically starts anapplication on the storage media. This allows even pre-school childrento use applications encoded on a storage media without adultsupervision.

It is currently possible to backup data stored in a hand-portableelectronic device such as a personal digital assistant (pda) or acellular mobile telephone to a personal computer. This can be achievedby connecting the hand-portable device to a computer either via aphysical serial data connection or a wireless connection such as IrDa orBluetooth. In some portable electronic devices data is stored, in part,in memory modules such as SD or MMC memory cards inserted into thedevice. This data can be backed up by removing the card from theportable device, inserting it into a data card reader connected to thepersonal computer, copying the data to the computer and then reinsertingthe card into the device.

The data stored on a computer can be backed up onto removable data mediasuch a CD-ROMs or DVD-ROMs, onto external hard drives or onto a server.It is known to have software running on the personal computer thatautomatically initiates a backup at a certain time. CMS market a backuphard drive, the ABSplus, which they claim is the only Automatic backupsystem on the market today. When the ABSplus is plugged into an AppleMacintosh computer it automatically initiates a complete backup of thecomputer's hard drive creating a fully bootable drive. Each time theunit is plugged in, powered on or scheduled, the ABSplus automaticallycopies only those files that have been changed or newly created sincethe last backup was performed. This unit, however, only has a singlededicated backup function, is relatively expensive and of a relativelylarge size compared to hand-portable electronic devices and is connectedto the computer via USB 2.0, Firewire or PCMIA.

It would be desirable to improve the facilities for backing-up datastored in the internal memory of a hand-portable device.

BRIEF DESCRIPTION OF THE INVENTION

According to one embodiment of the invention there is provided ahand-portable electronic device configured for hardware-initiatedautomated back-up, comprising: an internal memory for storing data; aninterface for connection and disconnection to any one of a plurality ofgeneric memory modules; a user interface that enables a user of thedevice to specify the generic memory module connected to the interfacefor automated back-up of data stored in the internal memory; acontroller for automatically backing up data, on connection of a genericmemory module to the interface, from the internal memory to theconnected generic memory module if the connected generic memory moduleis identified as a generic memory module that has previously beenspecified for back-up via the user interface.

According to another embodiment of the invention there is provided asystem for automated back-up of an internal memory of a hand-portableelectronic device, comprising: a generic memory module; and ahand-portable electronic device comprising: an internal memory forstoring data; an interface for connection and disconnection to any oneof a plurality of generic memory modules; a user interface that enablesa user of the device to specify a generic memory module connected to theinterface for automated back-up of data stored in the internal memory; acontroller for automatically backing-up data, on connection of a genericmemory module to the interface, from the internal memory to theconnected generic memory module if the connected generic memory moduleis identified as a generic memory module that has previously beenspecified for back-up via the user interface.

According to another embodiment of the invention there is provided amethod for backing-up data stored in an internal memory of ahand-portable electronic device, comprising: connecting thehand-portable device to a generic memory module; specifying the genericmemory module connected to the interface for automated back-up of datastored in the internal memory; backing up data from the internal memoryto the connected, specified memory module; disconnecting thehand-portable device from the specified memory module; automaticallybacking-up data from the internal memory to the specified memory module,whenever the specified memory module is subsequently connected to thedevice.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention reference will nowbe made by way of example only to the accompanying drawings in which:

FIG. 1 schematically illustrates a system for automatically backing-upan internal memory of a hand-portable electronic device on the insertionof a memory module into the device;

FIG. 2 schematically illustrates the process of specifying a memorymodule for automated back-up; and

FIG. 3 schematically illustrates the process of memory module initiatedautomated back-up.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

FIG. 1 schematically illustrates a system 2 for automatically backing-upan internal memory 12 of a hand-portable electronic device 10 on theinsertion of a memory module 4 into the device 10. The hand-portableelectronic device 10 is configured for hardware-initiated automatedback-up. The hardware that initiates the back-up is the memory module 4.

The memory module not only initiates an automated back-up when it isinserted into the device 10 but it also stores the backed-up data. Thememory module 4 is generic in the sense that it is not a type of memorythat is dedicated for back-up only but has additional more general uses.It is a type of memory that can be used for back-up but it can also beused in other applications in the device where data storage is requiredand can be used in devices that are not configured for hardwareinitiated automated back-up.

Typically the memory module is a memory card or memory stick thatcomprises non-volatile solid-state memory 6 such as, for example, FlashEEPROM memory. Examples of suitable memory modules are Secure Digital(SD) cards or Multi-Media Cards (MMC).

A particular memory module 4 can be specified for automated back-up of aparticular hand-portable electronic device 10 as described in moredetail below. Once the particular memory module 4 has been specified inthis way, whenever it is subsequently inserted into the particularhand-portable electronic device 10 it initiates automatic back-up ofdata from the internal memory 12 of the hand-portable device 10 to theinserted memory module 4.

As the back-up procedure is automatic when a specified memory module isinserted, it should be appreciated that although a memory module, beforeits specification for back-up, can be used for data storage other thanback-up in the hand-portable device 10, after specification for back-up,it will automatically be used for back-up whenever it is inserted.

The hand-portable device 10 is able to recognize an inserted memorymodule 4 as one that is specified for back-up for that device 10 byreading an identifier from the memory module 4. This identifier may bean identifier that uniquely identifies the memory module that ispermanently stored in the memory module 4, or, alternatively, it mayhave been written to the memory module 4 when it was specified forback-up.

The hand-portable electronic device 10 comprises: an internal memory 12for storing data including a data structure 26; an interface 16 forconnection and disconnection to an inserted memory module 4; a userinterface 18; and a processor 14.

The processor 14 is connected so that it can read from and write to theinternal memory 12. The processor 14 is also connected to the interface16, so that it can read from and write to the solid state memory 6 of aninserted memory module 4. The processor 14 is also connected to the userinterface 18.

The internal memory 12 stores computer program instructions 27 thatcontrol the operation of the hand-portable electronic device 10 whenloaded into the processor 14. The computer program instructions 27provide the logic and routines that enables the electronic device toperform the methods illustrated in FIGS. 2 and 3. The computer programinstructions may arrive at the hand-portable electronic device 2 via anelectromagnetic carrier signal that is received via a radio transceiver(not shown) or a galvanic connection or they may be copied from aphysical entity such as a computer program product, a memory device or arecord medium such as a CD-ROM or DVD.

The user interface 18 comprises a display 20 and a user input device 22.The user interface is used to provide a hierarchical menu for navigationby a user. The menu includes an option that enables a user of the device10 to specify an inserted memory module 4 for automated back-up. Thisoption is typically only available when a memory module 4 has beeninserted into the device 10. The hierarchical menu is consequentlyadaptive as it changes when an unspecified memory module 4 is insertedinto the device 10.

When an inserted memory module 4 is specified for back-up, the menu alsoprovides options for specifying which data stored in the internal memory12 is to be backed-up. For example, there may be an option to back-upall data and/or an option to back-up user-dependent data such ascontacts data.

The display 20 of the user interface 10 may notify the user when amemory module 4 has been inserted into the device and, after back-up ofdata to the inserted memory module 4, may notify the user to remove thememory module 4. This ensures that the backed up data is removed andstored separately from the data in the internal memory 12, so that lossof the device 10 does not result in loss of the backed-up data.

The processor 14 operates as a controller for automatic back-up. Itcontrols the automatic back-up of data, on connection of a memory module4 to the interface 16. This connection occurs automatically when thememory module 4 is inserted into the device 10.

The processor 14, on insertion of a memory module 4, attempts toidentify whether the inserted memory module has previously beenspecified for back-up by the device 10.

If the connected memory module is identified as a memory module that haspreviously been specified for back-up, then the processor 14automatically reads data from the internal memory 12 and writes it tothe memory 6 of the connected memory module 4. Once the back-up iscomplete, the processor 14 controls the display 20 to display a reminderto the user to remove the memory module 4 from the device 10.

If the connected memory module is not identified as a memory module thathas previously been specified for back-up, then the processor 14automatically adapts the menu presentable by the user interface 18 toinclude an additional option for specifying the inserted memory module 4for back-up. This option will not typically be presented automaticallywhen a memory module is inserted. Some navigation of the menu will berequired to be presented with this new additional option.

The interface 16 comprises galvanic contacts that mate withcorresponding galvanic contacts on an inserted memory module 4 to forman electrical connection between the interface 16 and the memory module4. In one embodiment, sensing circuitry is used to sense the change inan electrical characteristic (resistance or capacitance) of theinterface's galvanic contacts when they connect to those of the memorymodule 4. The sensing circuitry can therefore detect the formation of aconnection between the interface 16 and an inserted memory module 4.Other mechanisms may alternatively be used to detect the formation ofsuch a connection. For example, the hand-portable device 10 may comprisea slotted aperture to a receptacle for receiving the memory module 4, ifit's a card. The receptacle may include a mechanical switching elementthat is switched when a memory module 4 is fully inserted into thereceptacle.

The memory 12 is used to store a data structure 26. This data structurestores the identifier of each memory module 4 that has been specifiedfor back-up and stores, in association with each identifier, details ofwhat data has been specified for automated back-up when the memorymodule identified by that identifier is inserted into the device 10.

The processor 14 uses the data structure 26 to identify when the newlyconnected memory module 4 is one that has previously been specified forback-up. The processor 14 automatically attempts to read predetermineddata from a memory module 4 as soon as it has been inserted. The readdata is compared to the identifier(s) stored in the data structure 26.If there is a match a back-up is automatically started by the processor14. The processor 14 backs up to the inserted memory module 4 the datathat is specified in the data structure in association with the matchedidentifier.

In a first embodiment, when the user specifies an inserted memory modulefor automated back-up via the user interface, the processor writes anidentifier to a predetermined memory address of the memory module 4 andto the data structure 26. The identifier may have a predeterminedcontent. When a memory module 4 is subsequently inserted, the processor14 automatically attempts to read data from the predetermined memoryaddress of the memory module 4. The read data is then compared to theidentifier stored in the data structure 26. If the read data matches thestored identifier then it is determined that the inserted memory module4 has previously been specified for automated back-up.

In a second embodiment, when the user specifies an inserted memorymodule 4 for automated back-up via the user interface 18, the processor14 reads an identifier from a predetermined memory address of the memorymodule 4 and writes it to the data structure 26. The identifier may bepermanently stored in and uniquely identify the memory module 4. When amemory module 4 is subsequently inserted, the processor 14 automaticallyattempts to read data from the predetermined memory address of thememory module 4. The read data is then compared to the identifier storedin the data structure 26. If the read data matches the stored identifierthen it is determined that the inserted memory module 4 has previouslybeen specified for automated back-up.

The process of specifying a memory module is schematically illustratedin FIG. 2. At step 40, the user inserts a memory module into thehand-portable device. At step 42, the device 10 detects the presence ofa memory module 4 that has not previously been specified for back-up andadapts its hierarchical menu to include an option for specifying aninserted memory module 4 for automated back-up. At step 44, the usernavigates the menu and selects the option that specifies the insertedmemory module for automated back-up. Then at step 46, the device 10creates a new entry in the data structure 26 that includes an identifierfor the currently inserted memory module 4. This identifier may haveoriginated in the device 10 or in the memory module 4. Then at step 48,the user specifies what data should be automatically backed up when thecurrently inserted memory module 4 is inserted in the future. The usermay specify that all or some of the data should be backed up. At step50, the device 10 enters this information into the new entry in the datastructure 48. At step 52, the device performs a back-up of the specifieddata from the internal memory 12 to the inserted memory module 4. Aftercompletion of the back-up, at step 54, the device 10 displays a noticethat reminds the user to remove the memory module 4 from the device 10.At step 56, the user removes the memory module 4 from the device 10.

The process of hardware initiated automated back-up is schematicallyillustrated in FIG. 3. At step 60, the user inserts a memory module intothe hand-portable device. At step 62, the device 10 detects the presenceof the memory module 4. At step 64 the device determines whether theinserted memory module is one that has previously been specified forback-up. It reads data from the memory module 4 and compares it withidentifier data in the data structure 26. If a match is found theprocess moves to step 70, if no match is found the process moves to step66.

At step 66, the device 10 adapts its hierarchical menu to include anoption for specifying an inserted memory module 4 for automated back-up.The user if they wish navigate to this option and perform the processillustrated in FIG. 2.

At step 70, the information identifying the data specified for back-upis read from the data structure 26 and the back-up of the specified datafrom the internal memory 12 to the inserted memory module is initiated.After completion of the back-up, at step 72, the device 10 displays anotice that reminds the user to remove the memory module 4 from thedevice 10. At step 74, the user removes the memory module 4 from thedevice 10.

In the above described implementation, the memory module is used onlyfor back-up after it has been specified for backup and is removed afterbackup is complete. However, in other implementations, the memory modulemay be used for backup and for normal data storage, other than backup,after its specification for backup. In this implementation the memorymodule is not necessarily removed immediately after backup but remainsand is used for data storage. In this implementation, the user may atstep 48 create a folder in the memory of the inserted memory module 4that is used for backup purposes. This allows the new folder to be usedfor automatic backup and other folders to be used for storing data in anormal way so that pictures, sound etc can be saved directly to theinserted memory module. In this implementation, after completion of theback-up, at step 54/72, the device 10 need not necessarily display anotice that reminds the user to remove the memory module 4 from thedevice 10. The memory module 4 may remain in the device 10 andsubsequently can be used for storing data and need not be immediatelyremoved as illustrated in step 56/74. Thus in FIG. 2, the process may ormay not include the step 54 of displaying a reminder and step 56 isde-coupled from steps 53 and 54. Likewise in FIG. 3, the process may ormay not include the step 72 of displaying a reminder and step 74 isde-coupled from steps 70 and 72.

In some implementations of the invention, the only automated backupfacility that is available on the device 10 is that initiated byinserting a specified memory module 4. In this case, automated backuponly occurs on insertion of a specified memory module 4 and not at anyother time.

As the back-up procedure is automatic when a specified memory module isinserted, it should be appreciated that although a memory module, beforeits specification for back-up, can be used for data storage, other thanback-up, in the device 10, after specification for back-up, it willautomatically be used for back-up whenever it is inserted.

It will be appreciated in the foregoing, that in the implementationdescribed different memory modules may be used to back-up different datastored in the device 10. However, in other implementations only the useof a single memory module 4 for back-up is supported.

Although embodiments of the present invention have been described in thepreceding paragraphs with reference to various examples, it should beappreciated that modifications to the examples given can be made withoutdeparting from the spirit and scope of the invention.

Whilst endeavoring in the foregoing specification to draw attention tothose features of the invention believed to be of particular importanceit should be understood that the Applicant claims protection in respectof any patentable feature or combination of features hereinbeforereferred to and/or shown in the drawings whether or not particularemphasis has been placed thereon.

1. A hand-portable electronic device configured for hardware-initiatedautomated back-up, comprising: an internal memory for storing data; aninterface for connection and disconnection to any one generic memorymodule of a plurality of generic memory modules; a user interface thatenables a user of the device to specify the generic memory moduleconnected to the interface for automated back-up of data stored in theinternal memory; and a controller for automatically backing up data, onconnection of the generic memory module to the interface, from theinternal memory to the connected generic memory module if the connectedgeneric memory module is identified as a generic memory module that haspreviously been specified for back-up via the user interface.
 2. Ahand-portable electronic device as claimed in claim 1, configured todetect a newly connected generic memory module to the interface; andconfigured to identify when the newly connected generic memory module isa generic memory module that has previously been specified for back-upvia the user interface, wherein the controller is configured to performautomatic back-up if the newly connected generic memory module isidentified as a generic memory module that has previously been specifiedfor back-up via the user interface and to not perform automatic back-upif the newly connected generic memory module is not identified as aparticular generic memory module that has previously been specified forback-up via the user interface.
 3. A hand-portable electronic device asclaimed in claim 2, wherein the controller is operable, in response to aspecification via the user interface of a connected data module as adata module for automated back-up, to store at a predetermined memoryaddress of the data module a predetermined identifier and issubsequently operable to identify a newly connected generic memorymodule as one specified for automated back-up by reading data from thepredetermined memory address of the newly connected data module and bycomparing the read data with the predetermined identifier.
 4. Ahand-portable electronic device as claimed in claim 2, wherein thecontroller is operable, in response to a specification via the userinterface of a connected data module as a data module for automatedback-up, to read from the data module an identifier of the data modulepermanently stored in the data module and to store the read identifierin a data structure in the internal memory and is operable to identify anewly connected generic memory module as one specified for automatedback-up by reading the identifier from the memory module and comparingthe read identifier with the identifier stored in the data structure. 5.A hand-portable electronic device as claimed in claim 1, wherein thedevice has a body and is configured to enable user-controlled insertionof a memory module into the body of the device to form a connection withthe interface and user-controlled removal of the inserted memory modulefrom the body to disconnect the inserted memory module from theinterface.
 6. A hand-portable electronic device as claimed in claim 1,wherein a generic memory module is additionally usable for data storagein devices that are not configured for hardware initiated automatedback-up.
 7. A hand-portable electronic device as claimed in claim 1,wherein a generic memory module, before specification for back-up, isusable for data storage, other than back-up, in the device.
 8. Ahand-portable electronic device as claimed in claim 1, wherein a genericmemory module, after specification for automated back-up of data, isadditionally usable for data storage, other than backup, in the device.9. A hand-portable electronic device as claimed in claim 1, wherein amemory module is a memory card comprising solid state memory.
 10. Ahand-portable electronic device as claimed in claim 1, wherein the userinterface is used to specify which of the data stored in the internalmemory are to be backed-up.
 11. A hand-portable electronic device asclaimed in claim 1, wherein the user interface reminds the user todisconnect the memory module from the interface after automated back-upis completed.
 12. A computer program comprising program instructionswhich, when loaded into a processor, provide the controller of claim 1with said program instructions for said automatically backing up data.13. A system for automated back-up of an internal memory of ahand-portable electronic device, comprising: a generic memory module;and a hand-portable electronic device comprising: an internal memory forstoring data; an interface for connection and disconnection to any oneof a plurality of generic memory modules; a user interface that enablesa user of the device to specify a generic memory module connected to theinterface for automated back-up of data stored in the internal memory;and a controller for automatically backing-up data, on connection of ageneric memory module to the interface, from the internal memory to theconnected generic memory module if the connected generic memory moduleis identified as a generic memory module that has previously beenspecified for back-up via the user interface.
 14. A generic memorymodule for use in the system of claim
 13. 15. A method for backing-updata stored in an internal memory of a hand-portable electronic device,comprising: connecting the hand-portable device to a generic memorymodule; specifying the generic memory module connected to the interfacefor automated back-up of data stored in the internal memory; backing updata from the internal memory to the connected, specified memory module;disconnecting the hand-portable device from the specified memory module;automatically backing-up data from the internal memory to the specifiedmemory module, whenever the specified memory module is subsequentlyconnected to the device.
 16. A method as claimed in claim 15, furthercomprising: detecting a connection of a generic memory module to thehand-portable device; and identifying the connected generic memorymodule as a particular generic memory module that has previously beenspecified for back-up via the user interface.
 17. A method as claimed inclaim 16, further comprising: storing a predetermined identifier at apredetermined memory address of a data module connected to thehand-portable device, wherein the identifying of the connected genericmemory module comprises: reading data from the predetermined memoryaddress of the connected generic memory module; and comparing the readdata with the predetermined identifier.
 18. A method as claimed in claim16, further comprising: reading, from a data module connected to thehand-portable device, an identifier of the data module that is stored inthe data module, and storing the read identifier in a data structure inthe internal memory, wherein the step of identifying the connectedgeneric memory module comprises: reading the identifier from the genericmemory module; and comparing the read identifier with the identifierstored in the data structure.
 19. A method as claimed in claim 15,inserting a memory connecting the hand-portable device to a genericmemory module comprises inserting a memory module into a body of thehand-portable device and disconnecting the hand-portable device from theinserted generic memory module comprises removing the inserted memorymodule from the body of the hand-portable device.
 20. A method asclaimed in claim 15, wherein a generic memory module is usable for datastorage in other devices then the hand-portable device that are notconfigured for hardware initiated automated back-up.
 21. A method asclaimed in claim 15, wherein a generic memory module, beforespecification for back-up, is usable for data storage, other thanback-up, in the hand-portable device.
 22. A method as claimed in claim15, wherein a generic memory module, after its specification forautomated back-up of data, is additionally usable for data storage,other than backup, in the hand-portable device.
 23. A method as claimedin claim 15, further comprising, when the back-up has been completed,notifying the user that the memory module should be disconnected.
 24. Amemory module storing data for initiating an automated back-up when thememory module is connected to hand-portable electronic device as claimedin claim
 1. 25. A computer program comprising program instructions whichwhen run on a processor provide: means for enabling a user to specify ageneric memory module for automated back-up of data; and control meansfor automatically initiating back up of data, on connection of a genericmemory module to the interface, from an internal memory to the connectedgeneric memory module if the connected generic memory module isidentified as a generic memory module that has previously been specifiedfor back-up.
 26. A computer program as claimed in claim 25 furthercomprising program instructions which when run on a processor furtherprovide: identifier means for identifying when a newly connected genericmemory module is a generic memory module that has previously beenspecified for back-up, wherein the control means is responsive to theidentifier means to perform automatic back-up if the newly connectedgeneric memory module is identified as a generic memory module that haspreviously been specified for back-up and the control means does notperform automatic back-up if the newly connected generic memory moduleis not identified as a particular generic memory module that haspreviously been specified for back-up.
 27. A computer program as claimedin claim 26, wherein the control means is operable, in response to thespecification of a connected data module as a data module for automatedback-up, to store at a predetermined memory address of the data module apredetermined identifier and wherein the identifier means issubsequently operable to identify a newly connected generic memorymodule as one specified for automated back-up by reading data from thepredetermined memory address of the newly connected data module and bycomparing the read data with the predetermined identifier.
 28. Acomputer program as claimed in claim 26, wherein the control means isoperable, in response to the specification via the user interface of aconnected data module as the data module for automated back-up, to readfrom the data module an identifier of the data module permanently storedin the data module and to store the read identifier in a data structurein the internal memory and wherein the identifier means is operable toidentify a newly connected generic memory module as one specified forautomated back-up by reading the identifier from the memory module andcomparing the read identifier with the identifier stored in the datastructure.
 29. A physical entity embodying the computer program asclaimed in claim
 25. 30. An electromagnetic carrier signal carrying thecomputer program as claimed in claim 25.